Service Desk permissions override ‘manage sprint’ permissions

 Issue Description

If the filter query for a scrum board is deemed by JIRA to be too complex and Service Desk projects exist, users outside the Service Desk Agent group are unable to manage sprints. This behavior is also present when a user has “manage sprint” permissions for every project in the instance.  

 Steps to Reproduce

1. Create a board filter that does not specify a project which triggers a complex filter status.(ex. customfield = value1 ORDER BY Rank ASC)
2. Create Service Desk project
3. Grant “Manage Sprint” permission to a user on all projects.
4. Log in with the user and attempt to create/start/complete a sprint. They are unable to do so. 

 Expected Results

Since the “manage sprint” permission is granted to the user for all projects that exist, the user should be able to create/start/complete sprints.

Actual Results

The user is unable to create/start/complete sprints. The buttons are greyed out with a message “You need the manage sprint permission for all projects in the origin board to create a sprint”.

The “manage sprint” permission is overridden by Service Desk permissions, and requires the user to be in the “Service Desk Agent” group to manage sprints.  This occurs when a Service Desk project exists, even if no issues exist for that project.   

Workaround

1. Grant users Service Desk Agent permission.

     OR

      2. Edit the board filter in a way that the Service Desk project is excluded. For example, if the board filter is:

assignee in membersOf(jira-administrator)

We can change to:

Project not in (Service Desk Project 1, Service Desk Project 2, ......) AND assignee in membersOf(jira-administrator)